Prevent VSCode from breaking default extension sourcemap references - #709
Merged
Conversation
kaisalmen
approved these changes
Sep 29, 2025
kaisalmen
left a comment
kaisalmen
left a comment
Collaborator
There was a problem hiding this comment.
LGTM. I will test it with mlc.
|
🎉 This PR is included in version 21.3.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The VSCode default extension build process replaces the local sourcemap references by links to
https://main.vscode-cdn.net/sourcemaps/XXXIt's an issue because:
undefinedinstead of the VSCode commitI'm not sure why microsoft is doing such transformation 🤷
The change prevent vite from logging a lot of sourcemap errors